Record Status Mapping Registry entry

Maps record statuses defined by the Queensland Registry to default record statuses in Vitalware. Required to ensure the correct processing of registrations and orders, which are governed by the default record statuses defined in Vitalware.

Note: Only for use by the Queensland Registry of Births, Deaths and Marriages.

The background processing of registrations and orders in Vitalware is governed by a set of record statuses that are defined in Vitalware: the status of a registration and order determines how it is processed.

The Queensland Registry has added two record status fields to registration, POS and Orders modules in order to achieve greater granularity with record and product statuses. In this example we see two additional status fields for products:

Note: In POS, the additional status fields relating to records are found on the Payments tab.

As background processing of registrations and orders is governed by the default Vitalware statuses, it is necessary that the additional Queensland status fields are mapped to a default Vitalware status.

The Record Status Mapping Registry entry specifies the mapping between the Primary Status and Secondary Status fields and default Vitalware statuses.

Usage

There are two versions of this entry:

  • Record status: mapping Primary Status and Secondary Status fields in a registration module or POS module to a Vitalware status:
    KeyGroup
    Key 1Group
    Key 2Default
    Key 3Table
    Key 4table
    Key 5Record Status Mapping
    Key 6primary status
    Key 7secondary status
    ValueVitalware status
  • Product status: mapping Primary Status and Secondary Status fields for orders in the POS module to Vitalware statuses (table is always eorders):
    KeyGroup
    Key 1Group
    Key 2Default
    Key 3Table
    Key 4eorders
    Key 5Record Status Mapping
    Key 6primary status
    Key 7secondary status
    Key 8prodcode
    ValueVitalware status

where:

table

is a Registration module or POS module. See Example 1 below.

Note: When mapping status fields for products, table is always eorders. See Example 2 below.

primary status

is a status defined for the Primary Status field in table.

secondary status

is a status defined for the Secondary Status field in table.

prodcode

is a product code (specified in the Products module).

This key is only used if table is eorders. See Example 2 below.

Vitalware status

is a default Vitalware record or order status (defined in the record Status or order Status fields).

This entry maps Primary and Secondary statuses in the Births registration table to a default Vitalware status:

KeySetting
Key 1 Group
Key 2 Default
Key 3 Table
Key 4 ebirths
Key 5 Record Status Mapping
Key 6 Finalised
Key 7 Cancelled - Corrupt Data
Value Cancelled

When Primary Status is set to Finalised and Secondary Status is set to Cancelled - Corrupt Data, the Vitalware Record Status is set to Cancelled.

This entry maps Primary and Secondary statuses for a product order (for Marriage Certificates) to a default Vitalware status:

KeySetting
Key 1 Group
Key 2 Default
Key 3 Table
Key 4 eorders
Key 5 Record Status Mapping
Key 6 Finalised
Key 7 Eligibility - Inappropriate association
Key 8 ccpm
Value Applicant not related

When Primary Status is set to Finalised and Secondary Status is set to Eligibility - Inappropriate association and the ordered product is ccpm (Marriage Certificate), the Vitalware Product Status is set to Applicant not related.

Related Topics Link IconAll Queensland Registry entries